**************************************************************************
(C) COPYRIGHT International Business Machines Corp. 1994-1998
All Rights Reserved.
Licensed Materials - Property of IBM.
**************************************************************************
FILE: README

**************************************************************

PTF NP00945 (this PTF) applies to the Configuration Program for
2210. Customers that use APPN must have PTF02 or later installed
on the 2210.

**************************************************************
PTF NP00945 IS A MANDATORY PTF FOR ALL CUSTOMERS UPGRADING
from: 2210 MRS V1R1
to: 2210 MRS V2R2
-or-
from: 2210 MRS V2R1
to: 2210 MRS V2R2
**************************************************************

PTF NP00945 is a cumulative service PTF and replaces all previous
PTFs (NP00880, NP00881, NP00882, NP00883, NP00884, and NP00930) and 2210 MRS V2R2.
Customers that use the APPN features of the 2210 must have PTF02
or later installed on the 2210 when using this PTF.

The IBM Nways Multiprotocol Routing Services Configuration Program
Version 2.2 is a replacement for IBM Nways Multiprotocol Routing Services
Configuration Program Version 2.1 and all of the IBM Nways
Multiprotocol Routing Network Services Configuration Programs.

The Nways Multiprotocol Routing Services Configuration Program User's
Guide is available separately (GC30-3830).

The IBM 2210 Multiprotocol Router Services Configuration Program Version
2.2 (hereby referred to as the Configuration Program) is shipped on 12
diskettes and also a CD-ROM.
- Diskettes 1-6 contain the GUI Configuration Program
- Diskettes 7-10 contain the headless Configuration app file
- Diskettes 11-12 contain the WIN32S specific programs

- The CD-ROM contains a directory called config which contains all the
files for installing the Configuration Program for any of the three
supported operating systems.

This Configuration Program is co-required to configure any of the MRS
Router software loads for MRS V2.2.

Table of Contents:

1. WIN32S(needed for MS-Windows 3.1x)
2. Migration support for downlevel configuration files
3. Installation Files
4. Fonts
5. Initialization Files
6. Problem Determination
7. IBM Xstation Setup
8. Anonymous ftp site for IBM 2210 Multiprotocol Router
9. Using the Configuration Program
10. Restrictions
11. Installing the Configuration Program
12. Hardware and Software Requirements
13. Sending/Retrieving the Configuration file
14. CDB File Locking Enhancement
15. Using the Configuration Program command line and headless functions
16. ASCII Read function restrictions
17. APARs (problems) fixed in this Configuration Program


1. WIN32S

NOTE: The WIN32S diskettes are only needed for running the Configuration
Program on MS-Windows 3.1x workstations. If you have not already installed
WIN32S, you must do so in order to run the Configuration Program on this
platform.


WIN32S Install Instructions:
1.Stop all Windows applications
2.In Windows Program Manager, select FILE, then RUN...
3.Put diskette 11 of 12 in diskette drive A:
4.In Command Line (of RUN...) enter: A:SETUP and press OK.
5.Note message to add SHARE.EXE to AUTOEXEC.BAT file (SHARE is
part of DOS; the AUTOEXEC.BAT file can be modified after this
install).
6.At next prompt for the WIN32S Setup diskette, insert 12 of 12.
7.Expect message "WIN32S files successfully installed".
8.Optional FREECELL program is on diskette 11 of 12.
9.SETUP will restart WINDOWS to complete the installation.


2. MIGRATION SUPPORT FOR DOWNLEVEL CONFIGURATION FILES

To use configuration files created by earlier versions of
the configuration program, you MUST migrate to the new
release format. If the only copy of the configuration is
either in the router or in binary format, you must use
the version of the configuration program that created the
configuration to create the configuration database file.

Creating Configuration Database File
To create the configuration database file:
1. Start the previous version of the configuration program.
2. Select READ ROUTER CONFIGURATION to read the existing
configuration into the configuration program. Another
way to load an existing configuration into the
program is to select COMMUNICATION, SINGLE, and then
RETRIEVE from the Configuration menu.
3. Select SAVE CONFIGURATION from the File menu.
4. Save the configuration into a file with file extension .CDB.

Converting a Configuration Database File
Configurations already in a configuration database may be
migrated to the new release format by:
1. Starting the current version of the configuration program.
2. Selecting OPEN CONFIGURATION from the File menu.
Select the old configuration from within the .cdb
file you created in "Creating Configuration Database
File." The configuration program will then ask if you
wish to convert the configuration to the new format.
3. Selecting SAVE CONFIGURATION AS to save the configuration
to a new file with a new name. Using the "Save configuration
as" function allows you to keep the existing configuration
file for future use.

Router configuration format(readable by 2210)

If you did not save ".cdb" files using the previous versions of the
Configuration Programs, you should find a copy of the Configuration
Program which matches your router software to create ".cdb" files.
The Configuration Program will check the level of the configuration
at the beginning of a READ ROUTER CONFIGURATION or RETRIEVE, and
terminate the read if the level of the configuration does not match
the level of the Configuration Program.


3. Installation Files

Refer to the "Installing the Configuration Program" section for
instructions on how to install the Configuration Program. When you
install the Configuration Program, several files will be copied to the
installation directory. IT IS CRITICAL THAT YOU HAVE WRITE PERMISSION
TO THE INSTALLATION DIRECTORY TO INSTALL AND USE THE CONFIGURATION
PROGRAM. The Configuration Program writes the program files to the
installation directory during installation. During program execution,
the Configuration Program writes to the installation directory such
information as the font and colors to use in the program. The
Configuration Program also writes files to the installation directory
when creating or reading a configuration and in the event of an
"Internal execution error". Additionally, the Configuration Program
can write files ending with the extensions "cdb" or "mdb" to the
installation directory when saving a configuration or sending multiple
configurations to 2210 routers. These files are in binary format and
should not be changed via a file editor or with an AIX command.

4. Fonts

Font requirements for AIX

The configuration program requires specific X11 fonts.
When the configuration program starts, it looks for the
Helvetica, Times Roman, and New Century Schoolbook fonts
in the /usr/lib/X11/fonts/75dpi directory. The font files
have the following names:

helv*.Z
tim*.Z
ncen*.Z

After the configuration program starts, you can access
any font supported by your system. If you select an
unusual font style, or very large font size, you may lose
the ability to read the panels or make selections from
them. See the following procedures to recover from font problems.

a.Open the directory that contains the Configuration Program and
edit the CFG.INI file. Search for the line that reads
FONTSIZE=xx(where xx is a font size) and change the parameter to
FONTSIZE=14. For AIX systems, search for the line that reads
FONTFAMILY=xxx (where xxx is a font name) and change the parameter to
FONTFAMILY=helvetica. For systems using Windows, change the
parameter to FONTFAMILY=system.

b.For AIX systems, locate the AIX.INI file on the Configuration
Program diskettes or CD-ROM. Copy this file to the directory that
contains the Configuration Program and rename the file to CFG.INI.
For Windows systems, locate the WIN31.INI file on the Configuration
Program diskettes or CD-ROM. Copy this file to the directory that
contains the Configuration Program and rename the file to CFG.INI.

5. Initialization Files

The Configuration Program uses a user defaults file, cfg.ini, to
perform startup actions while loading the runtime image. Although
this file can be edited manually using a text editor (such as vi), it
is recommended that you make changes to the user defaults file by
using the dialogs Set font, Set Colors and Set default model, found
under the Options item in the Menu bar. The cfg.ini file will be
written when you press the Ok button.

If a cfg.ini file is not in the installation directory, the default
attributes will be used and the cfg.ini file will be re-created using
the defaults.

6. Problem Determination

The file, cfg.err on AIX systems, or CFG.ERR on DOS and OS/2 systems,
is created when an internal execution error occurs in the program.
This file will contain the program stack at the time the error
occurred. The contents of this file should be given to IBM support
when a problem with the Configuration program is reported. The
configuration files in all formats available should also be given to
IBM support to assist with problem determination.

NOTE: The above mentioned file is written to the directory from which
the Configuration Program was started.

7. IBM Xstation Setup

The monitor must have at least 640 x 480 resolution with 16 colors or
grey scales. In order to run the Configuration Program from an IBM
Xstation which is connected to an IBM RISC System/6000 host, you need
to have /usr/lib/X11/fonts/75dpi/ directory in the Font Path of your
Xstation. You can check to see if this directory is already in your
path by typing:

xset -q

Under Font Path, look for /usr/lib/X11/fonts/75dpi/ in the list of
directories.

If you do not have this directory in your Xstation Font Path then from
your Xstation type:

xset fp+ /usr/lib/X11/fonts/75dpi/

This will add the Configuration Program font directory to your
Xstation Font Path. For future use of the Configuration Program
through Xstations, place the above line in your .profile.

NOTE: If your font path is not set correctly, you may get an "out of
memory" error message.

8. Anonymous ftp site and web page for IBM 2210 Configuration Programs

IBM has established an anonymous ftp site for providing information
and configuration program updates (and in the future other program
updates) relating to the 2210.

The hostname for the anonymous ftp site is ftp.nways.raleigh.ibm.com.
If you have trouble resolving this name the IP address is
204.146.167.70. After connecting to the machine specify anonymous as
the user id and your e-mail address as your password. Check the
README file on the anonymous ftp site in the /pub directory for the
latest information.

The subdirectories where the Configuration Prorgrams reside are as
follows:

pub/config/2210/MRS/2.2.0/GA/diskettes for the diskette images
for PCs and Risc/6000s

pub/config/2210/MRS/2.2.0/GA/runtime for the RISC System/6000 files
(note that runtime files are now in tar.Z format)

There is also a 2210 Configuration program web page for users with web
browsers. The URL is listed below:

http://www.networking.ibm.com/support/code.nsf/2210code?OpenView


9. Using the Configuration Program

From the Navigation Window, under the Help pulldown, there is a
Tutorial available to help a new user get familiar with using the
Configuration Program. The Tutorial is also available in the
Configuration Window when 'Router' is selected from the Navigation
Window.

This chapter explains how to start and operate the Configuration
Program. This chapter also includes instructions for creating IBM
2210 configuration files and transporting them to the IBM 2210.

-Starting the Configuration Program

The procedure you follow for starting the Configuration Program
depends on whether your workstation is a RISC System/6000 workstation
or a PC workstation.

Starting the Configuration Program on AIX

Before starting the configuration program:
1. X-Windows** must be running on the workstation.
2. The fonts required by the configuration program must
be available. See "Font Requirements for AIX" on
page 9 for the font requirements.
3. /X11fnt.coreX.fnt must be installed to have access to
the MIT X11.5 (75-dp1 and 100-dou) fonts.

To start the configuration program:
1. Enter XINIT to start X-Windows, if not already started.
2. Change the current directory to the directory con-
taining the Configuration Program files, for example CD MRSC110.
3. Enter CFG. to display the title window for the configuration
program.

To start the headless version of the Configuration Program on AIX:
1. Change the current directory to the directory con-
taining the Configuration Program files, for example CD MRSC110.
2. Invoke the Configuration Program using either 'cfg -batch' with
the command line parameters in a file named cfgargs or list the
command line arguments directly after -batch. (Example below)
'cfg -batch -logMessages on -commandsFrom yourFile'


Starting the Configuration Program on OS/2 or Windows

1. Locate and open the configuration program folder.
2. Double-click on the Configuration Program icon to
start the program. The title window for the configuration
program will be displayed.

To start the headless version of the Configuration Program on OS/2 or
Windows:
1. Change the current directory to the directory con-
taining the Configuration Program files, for example CD MRSC110.
2. Invoke the Configuration Program using either 'cfg.exe headless.app'
with the command line parameters in a file named cfgargs or list the
command line arguments directly. (Example below)
'cfg.exe headless.app -logMessages on -commandsFrom yourFile'


10. Restrictions.

This section discusses some KEY considerations that users must be
aware of when creating valid configurations.

-You MUST make sure that TCP/IP is installed and RUNNING before using
the "Communications Single" and/or "Communications Multiple" functions.
On some platforms, the Configuration Program will hang if TCP/IP is
not installed and running.

-ELS (Event Logging System) data
The Configuration Program does not support ELS configurations. Thus,
if you want to configure ELS you must use the online configuration
program on the router. When reading configurations from the router,
the Configuration Program will preserve any ELS configuration done
in the online configuration on the router and send it back on a
subsequent send.


-AIX Version 3.2.5 or higher is now required for the Config Program.
Previous versions of the MRNS Config Program (V1R3.0 and earlier)
would not work with AIX Version 4.1 or higher. If you are not
sure which version of AIX you have currently, use the 'oslevel'
command. The output from the command for an AIX 3.2.5 system is '>3250'.
Some of the earlier versions of AIX do not support the 'oslevel' command.

The Configuration Program is not fully supported on OS/2 WARP 4.0.
Compatibility with OS/2 WARP 4.0 is considered a priority and is
being addressed. There are users that are using the Configuration
Program on OS/2 WARP 4.0, but they are using it at their own risk.

11. Installing the Configuration Program

This chapter provides instructions for installing the Configuration
Program.


-Installation on a RISC System/6000 (requires AIX 3.2.5 or higher)
==================================
To install the Configuration Program on a RISC System/6000 workstation
from CD-ROM:

STEP 1 Log in to AIX as a non-root user.

STEP 2 Place the CD-ROM in the drive and mount the CD-ROM file-
system.

STEP 3 Change directories to the cdrom filesystem and the config
subdirectory.

STEP 4 At the AIX prompt, type INSTALL.AIX and press ENTER.

STEP 5 Follow the prompts that appear on the screen to complete
the installation.


To install the Configuration Program on a RISC System/6000
workstation from Diskettes:

STEP 1 Log in to AIX as a non-root user.

STEP 2 Place diskette 1 in the 3.5-inch diskette
drive.

STEP 3 At the AIX prompt, type the following command:

NOTE: AIX is case-sensitive.

dosread -a INSTALL.AIX INSTALL.AIX

Where:

dosread Reads the file from a DOS diskette and places
it in the current directory.

-a Converts the DOS file to an AIX file.

install.aix Is the file name on the diskette.

install.aix Is the file name to be used in the AIX system.

If the install.aix command fails, it may indicate that the
current directory is not part of your search path. To
continue the install, type: ./INSTALL.AIX

STEP 4 Type: chmod 550 INSTALL.AIX

Where:

chmod Changes the file permissions given to the
owner and group.

550 Defines the permission types for a user, group,
and other users. In this case, the user and
group are allowed read and execute permission
and others are allowed only read permission.

install.aix Is the name of the file for which you are
changing the permissions.

STEP 5 At the AIX prompt, type INSTALL.AIX and press ENTER.

STEP 6 Follow the prompts that appear on the screen to complete
the installation.


-Installation on a PC
====================
Using OS/2


To install the Configuration Program on a PC workstation running
OS/2 2.1 or 3.0 and using the CD-ROM, follow these steps:

STEP 1 Place the CD-ROM in the drive.

STEP 2 At the OS/2 prompt, type X:OS2INST and press ENTER,
where X is the drive letter of the CD-ROM drive.

STEP 3 Follow the prompts that appear on the screen.


To install the Configuration Program on a PC workstation running
OS/2 2.1 or 3.0 and using diskettes, follow these steps:

STEP 1 Place diskette 1 in the diskette drive.

STEP 2 At the OS/2 prompt, type A:OS2INST and press ENTER.

STEP 3 Follow the prompts that appear on the screen.

The Configuration Program will install itself on the system and will
prompt you to enter the installation drive and directory. An IBM 2210
folder will be created with the Configuration Program icon inside.

NOTE: See the Restrictions section regarding OS/2 WARP 4.0


-Using Windows
=============

To install the Configuration Program from CD-ROM on a PC work-
station running Windows, type WIN X:INSTALL beside the DOS prompt
where X is the drive letter of the CD-ROM drive or follow these steps:

Windows 95 Instructions for CD-ROM installation

STEP 1 Start Windows 95
STEP 2 Place the CD-ROM in the drive.
STEP 3 Double click on the MyComputer icon.
STEP 4 Double click on the CD-ROM icon.
STEP 5 Double click on the config directory.
STEP 6 Double click on the Install.exe icon.
STEP 7 Follow the prompts that appear on the screen.

To install the Configuration Program from diskettes on a PC work-
station running Windows, type WIN A:INSTALL beside the DOS prompt or
follow these steps:

Windows 95 Instructions

STEP 1 Start Windows 95
STEP 2 Place diskette 1 in the diskette drive.
STEP 3 Double click on the MyComputer icon.
STEP 4 Double click on the 3 1/2 Floppy[A:] icon.
STEP 5 Double click on the Install.exe icon.
STEP 6 Follow the prompts that appear on the screen.

Windows 3.1x Instructions

NOTE: If you have not installed the WIN32s diskettes (required for
Windows 3.1x only), you must do so BEFORE installing the Configuration
Program.

STEP 1 Start Windows.
STEP 2 Place diskette 1 in the diskette drive.
STEP 3 Select FILE from the menu bar.
STEP 4 Select RUN from the pull-down window.
STEP 5 Type A:INSTALL on the command line and select OK to start
the installation.
STEP 6 Follow the prompts that appear on the screen.


The Configuration Program will install itself on the system disk drive
and will prompt you to enter the installation directory, group box
name, and any other details necessary to complete the installation.

After a successful installation, an icon labeled 'MRS V2.2 Config'
will be added to the program group you specify using the installation
program or, by default, to the IBM 2210 program group. In addition,
an icon is now provided for the README file as well.

NOTE: In subsequent installations, the settings for the exiting icon
for the current release will be changed to reflect the new installation
and working directories.

To delete one of the icons, follow these steps:

Windows 95 Instructions

STEP 1 Single left mouse click on Start icon.
STEP 2 Move mouse pointer over Settings.
STEP 3 Single left click on Taskbar.
STEP 4 Single left click on Start Menu Programs.
STEP 5 Single left click on Remove.
STEP 6 Single left click on the + icon beside IBM 2210 to expand.
STEP 7 Single left click on MRS V2.2 Config.
STEP 8 Single left click on Remove.

Windows 3.1x Instructions

STEP 1 Select the icon that you want to delete.
STEP 2 Select FILE from the menu bar.
STEP 3 Select DELETE from the cascade menu.
STEP 4 An information message window is displayed. Select YES to
delete the icon.

Files copied during installation

When you install the Configuration Program on a RISC System/6000 or
PC workstation, a number of files are copied to the installation
directory. The installation directory will be named by default mrsxxx
where xxx is the version number. If you have deleted the icon in the
steps above and would like to complete the clean up, you should also
delete the files in the installation directory. The files that are
copied vary according to the type of workstation you are using. If you
want to change the name of the installation directory, provide the name
you prefer before installing the Configuration Program files.


12. Hardware and Software requirements

Hardware and Software requirements for the RISC System/6000

The following hardware and software are required to run the
Configuration Program on the RISC System/6000 work-station:

-IBM AIX 3.2.5 or higher with Transmission Control Protocol/Internet
Protocol (TCP/IP) enabled

-IBM AIXwindows*
-16 MB of memory (32 MB recommended)
-3.5-inch diskette drive that can read and write 1.44-MB formatted
diskettes or a CD-ROM drive.
-22 MB of available space on the fixed disk drive
-A graphics display that supports 640*480 resolution and 16 colors
or gray scales (1024*768 resolution and 256 colors recommended)
-A mouse

Hardware and Software requirements for the PC

The following hardware and software are required to use the
Configuration Program on a PC workstation using an Intel** 80386**
or higher processor or a compatible system that has an Intel 80386 or
higher processor (486 DX2-50 is the minimum recommended processor).

For workstations running the Microsoft** Windows** program, you need:

-IBM DOS 5.0 or higher, MS-DOS 5.0 or higher
-Microsoft Windows 3.1 or later versions
o Win32s, included with the MRNS Configuration Program diskettes
Not needed by Windows 95
o WinSock 2.0 DLL (included with Win32s)
-TCP/IP application that uses WinSock 2.0
(This is only required for using the Communications functions)
-16 MB of memory (32 MB recommended)
-3.5-inch diskette drive that can read and write 1.44 MB-formatted
diskettes or a CD-ROM drive.
-22 MB of available space on the fixed disk drive
-A graphics display that supports 640*480 resolution or higher and 16
colors or gray scales (1024*768 resolution and 256 colors recommended)
-A mouse
-If you encounter problems with windows not updating properly, ensure
that you have installed the latest BIOS and video drivers provided
by the manufacturer.


For workstations running the IBM Operating System/2 (OS/2) program,
you need:

-OS/2 2.1 or WARP 3.0, see Restrictions about OS/2 WARP 4.0
-IBM TCP/IP 1.2.1 for OS/2 or later (This is only required for using
the Communications functions)
-16 MB of memory (32 MB recommended)
-3.5-inch diskette drive that can read and write 1.44-MB formatted
diskettes or a CD-ROM drive.
-22 MB of available space on the fixed disk drive
-10 MB of available swapper disk space on the swapper fixed disk
drive partition
-A graphics display that supports 640*480 resolution or higher and 16
colors or gray scales (1024*768 resolution and 256 colors recommended)
-A mouse
-If you encounter problems with windows not updating properly, ensure
that you have installed the latest BIOS and video drivers provided by
the manufacturer.


13. Sending/Retrieving the Configuration file

Note: It helps to step through the Configuration Program as you read
this.

You MUST make sure that TCP/IP is installed and RUNNING before using
the "Communications Single" and/or "Communications Multiple" functions.

The Communications function will communicate with the router using
the SNMP protocol. The router must be set up with an IP Address and
have a SNMP community with access defined as WRITE_READ_TRAP for send and
restart. For retrieve and query, the community access can be READ_TRAP or
WRITE_READ_TRAP.

The single send will send the configuration that is currently open. The
IP destination and community fields will default to what is defined in
the configuration. The timeout value is the maximum number of seconds
the send function will wait for a response. Select the appropriate
action(s):
1. Send the configuration to the router
2. Restart the router immediately or later
3. Send the configuration and then restart the router
4. Query the router for the System Description.
5. Retrieve the configuration from the router.

Query will get the system description from the router and display
the IP Address, version/release, system name, contact, location,
and up time. The four Communications functions are mutually exclusive
with the exception of Send and Restart, which can be used together.

The multiple send/retrieve will act on configurations that are saved in
the configuration database. The send lists (.mdb files) contain groups of
configuration names and parameters to be sent/retrieved. For each
configuration the parameters are: IP destination, community,
timeout, send, restart, date, time, query, and retrieve. For each entry,
the configuration can be sent, the router can be restarted immediately,
the configuration can be sent and the router restarted at a
later time, or the router can be queried for its System Description.
The configurations can also be retrieved from several routers into one
or more configuration databases.

To create a send list, type in the Send list name. Select the
'Show .cdb' button. Choose the database and configuration and select
the OK button. Select close to exit this screen. The IP destination
and community are initialized from the configuration's values. Any of
the fields can be edited. The field sizes can be changed by 'grabbing'
one of the bars in the header and dragging it left or right. The Send
and Restart functions are selected by default if you create a .mdb
entry in this manner.

The Add button will add an empty row at the bottom of the list.
The delete button will delete any selected row. The Save button will
save the configurations and their parameters into the send list.
If any row is selected, the new row (from Add or Show .cdb) will be
added after the selected row.

The Copy list button will copy the selected send list to a new send
list. The Delete list button will delete the selected send list. The
OK button will start the sending of configurations.

If 'Stop on error' is selected and an error occurs when sending a
configuration, an error message is displayed and all sending stops.
If it is not selected and an error occurs, the error message is
written in the file 'cfg.com' and the sending continues with the
next configuration.

If the router is queried and 'Stop on error' is selected, the
router's information is displayed and all sending/querying stops.
If the router is queried and 'Stop on Error' is not selected, the
system description is written in the file 'cfg.com' and the
sending/querying continues with the next configuration.

For single router restart, the time initializes to the current time
so the router will restart immediately. However the 'Date' and 'Time'
fields can be changed to any date and time. For multiple router
restart, the dates and times initialize to the last entered dates
and times for each row in the selected send list.

The 'All' button will apply the date and time specified in the
'Restart at' area to each row in the list. The 'Selected' button
will only apply the date and time specified in the 'Restart at'
area to the row selected. The date and time fields in the table may
also be directly edited. If the Restart box is selected for a row
and the date and time field are empty, the date and time will
default to the date and time in the 'Restart at' area.

Note: If the restart is sent to the router with a date and time
earlier than the current date and time on the workstation (for
example yesterday's date), the router will be restarted immediately.

The delayed restart time is sent to the router in the form of seconds
(xx). The router will restart at xx seconds from when he receives
the packet (within a two minute window). Therefore if there are many
hops to the destination or the network traffic is heavy, the router
may restart later than expected.

If a timeout error occurs, check that:
1. the IP Destination address is correct
2. there is a route to the IP address
3. the community exists
4. the timeout value is large enough

If an error with the SNMP packet occurs, check that:
1. the community has WRITE_READ_TRAP access
2. for multiple send, the configuration exists in the database


14. CDB File Locking Enhancement

A feature has been added to the config tool that locks the
config database (*.cdb) files while they are being accessed.
If two instances of the config tool write to the same
database at the same time, there was potential for the
database to be corrupted. With the new locking mechanism, a
tool trying to access the file will know when another tool
is already accessing it and wait for the file to become
available.

How it works

When the config tool reads or writes from a .cdb file, it
will add a lock entry to the lock file (creating a new lock
file if necessary). The lock file will have the same name
as the .cdb file, but with a .lok extension (ie ~/test.cdb
will have a lock file named ~/test.lok).

There are two types of lock entries: ReadLock and WriteLock.
It is ok for several tools to have a ReadLock on the same
.cdb file at the same time. The only times that a lock will
be denied are when a WriteLock is requested while a lock (read
or write) already exists on the file, or when a ReadLock is
requested while a WriteLock already exists on the file. This
prevents the case of two tools writing to the same file at
the same time, resulting in corruption.

The lock entry that is placed in the .lok file consists of
the lock type (ReadLock or WriteLock) and the person who
owns that lock. On UNIX platforms, the user@hostname will
be placed in the lockfile. On Windows or OS/2, the contents
of the environment variable 'CFGUSER' will be placed in the
lockfile. The locking mechanism will still work if the
CFGUSER environment variable is not set, but you will not be
able to tell who has the file locked. One good reason to
set CFGUSER, is if a machine goes down while the config tool
is accessing a .cdb file, the lock will remain in place and
must be removed from the file by hand (or by erasing the
.lok file). It will be easy to verify if the lock is
invalid if you know who owns the lock.

Setting the CFGUSER environment variable

UNIX users need not worry about this step as user@hostname
replaces this information.

From any Windows or OS/2 command line execute the following:

set CFGUSER=<your text here>

This command can also be placed in your AUTOEXEC.BAT file on
Windows, or CONFIG.SYS file on OS/2 so it is set every time
your machine boots.


15.Using the Configuration Program command line and headless functions

The headless configuration program is a windowless version
of the configuration program which can be used along with
the command line arguments to accomplish tasks in a 'batch'
mode. It uses the headless.app file instead of the cfg.app
file, which is used with the GUI version of the Configuration
Program. Because the windows do not have to come up, the
performance should be improved over the GUI version.

The command line options are listed from within the
Configuration Program under Help->On commands... from the
main menu bar. These arguments can be listed as parameters after
the command to invoke the Configuration Program, or put into
the default command line argument file 'cfgargs'. The 'cfgargs'
file will be read and executed if it exists, and then erased,
so keep a copy. The user may also put command line arguments
into a file of his choice and read them using the command line
argument '-commandsFrom userFile'.

There are a couple of command line restrictions that should be
noted. One is that the user cannot use * directly from the
command line. If the user wants to use a *, they must use it
from the cfgargs or other arguments file.

Another has to do with invoking the Configuration Program from
an AIX shell script. If the user wanted to update a parameter
on multiple routers in one command, he might create one argument
file with a series of -retrieve and -asciiWrite lines, one pair
per router. Then the user would create another argument file of
a different name with a series of -asciiRead and -send lines,
again one pair per router with the ascii file names and router
IP addresses matching those of the first argument file. When
the Configuration Program is invoked from an AIX shell script
it will look something like the following:

cfg.aix headless.app -commandsFrom argumentFile1
anotherScriptWhichDoesStreamEditingToChangeTheParameterForEachRouter
cfg.aix headless.app -commandsFrom argumentFile2

The restriction is that if you were to try to use 'cfg -batch'
instead of the 'cfg.aix headless.app', then the Configuration
Program would be started in the background and both the script
which does the stream editing(sed or awk) and the second
invocation of the Configuration Program would fail because the
ascii files would not exist yet.

16.ASCII Read function restrictions

The Configuration Program will only read ASCII files created with
the same version of the Configuration Program. Upgrade of
configurations from release to release must be done using the
.cdb format.

The Configuration Program User's Guide has a section 'Reading
Partial Configuration Files'. Do not do step 2, which says,
'Using a text editor, remove all groups that you are not changing.'
Currently, there are problems reading a partial configuration file.


17.APARs (problems) fixed in this Configuration Program

2210 MRS V2R2 PTF NP00945 December 1998
-------------------------

PTF NP00945 is a cumulative service PTF and replaces all previous
PTFs (NP00880, NP00881, NP00882, NP00883, NP00884, and NP00930) and 2210 MRS V2R2.
Customers that use the APPN features of the 2210 must have PTF02
or later installed on the 2210 when using this PTF.

The list of fixes below is ordered from the current PTF to the
oldest.  The fixes are cumulative.


NP00945   12/1998
           NA04023      CFG PGM ABENDS IF FRAME RELAY RECEIVE BUFFERS SET TO MORE THEN
           NA04442      CIRCUIT TYPE INCORRECT WHEN UPGRADING WAN REROUTE
           NA04443      COMPRESSION INCORRECT WHEN UPGRADE TO V2.2
           NA04444      NO MIGRATION PATH FROM VERSION 1.3 TO VER 2.2
           NA04623      CONFIG TOOL ONLY ALLOWS 24 BUFFERS TO BE DEFINED
           NA04670      MODEL 1S8 HANGS AFTER COLD START
           NA04707      WHEN INDICATING NO OSPF SECURITY CODE THE CONFIG USES ASCII 0
           NA04793      CONFIGURATOR CHANGES SDLC STATION RECEIVE WINDOW AND PACKET SIZ
           NA04920      PVC NAME FOR THE HIGHEST PORT MIGRATED TO LOWER PORT
           NA04955      ISDN RETRY DEFAULTS TO 23 BUT THE TOOL ONLY ALLOWS 0-10

NP00930   10/1998
           NA03361      HELP PANEL FOR DTE ADDRESS FIELD SAYS 16 DIGITS ALLOWED.
           NA03420      HELP PANEL FOR ISDN PRI SWITCH VARIANT IS INCORRECT
           NA03623      CONFIG TOOL COMMUNICATE TIMEOUT PARAMETER DISALLOWS DEFAULT
           NA04023      CFG PGM ABENDS IF FRAME RELAY RECEIVE BUFFERS SET TO MORE THEN
           NA04074      COMPRESS ORPHANS ON BY DEFAULT WHEN COMPRESSION NOT ENABLED
           NA04079      THE READ COMMAND DOES NOT WORK FROM THE CFGARGS FILE
           NA04207      RANGE FOR SDLC LEADING FLAGS NEEDS TO BE 0-120
           NA04370      WHEN YOU ADD AN ISDN 4PORT BRI, YOU GET ? ON THE INTERFACE

NP00884   08/1998
           NA03643      USER GETS MSG ACXE0643 BLOCK 15 RECORD 52
           NA04050      ADDING ADDITIONAL WAN ADAPTER WITH DIALS CAUSES BAD CONFIG
           NA04052      SOURCE ROUTER BRIDGING ON FRAME RELAY PVC S NOT STAYING CONFIGU
           NA04074      COMPRESS ORPHANS ON BY DEFAULT WHEN COMPRESSION NOT ENABLED
           NA04087      CONFIG TOOL DOES NOT ALLOW 8 CHARACTER STATION NAME
           NA04105      QLLC CALL USER DATA FIELD LIMITED TO 2 CHARACTERS, REQUIRES 16
           NA04145      V.25 BIS ADDRESS CAN BE CONFIGURED FOR A SINGLE ADDRESS NAME
           NA04202      CAN'T DELETE ATM ADAPTER VIA PORTOR SLOT PULL DOWN
           NA04208      ENHANCE COS RADIO BUTTON CHANGED FROM DISABLED TO ENABLED
           NA04240      WINDOW SIZE IS NOT ENOUGH TO SHOW ALL OPTIONS ON APPN INTERFACE

NP00883   06/1998
           NA03464      APPN CONFIG TOOL RTP INACTIVITY TIMER NEEDS TO BE IN SECONDS

NP00882   06/1998
           NA03369      CONFIG TOOL DISPLAYS ERROR ACXE0003 AFTER READING SAVED FILE.
           NA03555      MESSAGE ACXE0026 IS RECEIVED WHEN TRYING TO ADD A SECOND
           NA03697      CONFIGURING APPN OVER HPR DOES NOT ACTIVATE APPN OVER HPR
           NA03777      IPX NET.# RANGE FOR FILTERS SHOULD INCLUDE 0
           NA03788      APPN ON MPC+ ESCON TG CHARS EFFECTIVE CAPACITY DEFAULT TOO LOW
           NA03904      IF THERE IS A DIAL CIRCUIT DEFINED, THE UPGRADE OF CONF. FILE
           NA03935      USER CANNOT SEND DIFFERENT CONFIGURATIONS TO VARIOUS ROUTERS

NP00881   04/1998
           NA03271      THE DEFAULT FOR RPS SHOULD BE NO SO THAT IT DOESN T
           NA03324      CONFIG. TOOL SHOULD NOT ACCEPT THE SDLC LINK POLL DELAY IN INCR
           NA03330      WHEN USER DEFINES SECOND MULTI-LINK, GETS ERROR.
           NA03353      WHEN 1.1 CONFIG TOOL READS A CONFIG FROM THE ROUTER IT TRUNCATE
           NA03358      CANNOT ENTER MORE THAN 14 DIGITS IN DTE ADDRESS FIELD, X.25
           NA03369      CONFIG TOOL DISPLAYS ERROR ACXE0003 AFTER READING SAVED FILE.
           NA03419      CONFIG TOOL DOES NOT MATCH TALK 6 TOKEN RING MTU RANGE AND
           NA03428      ERROR ACXE003 MESSAGE WHEN CONFIGURING INTERFACE FOR FRAME RELA
           NA03441      TAKES OVER 2 MINUTES TO CONVERT ASCII TO BINARY FILE VIA AIX MA
           NA03467      WINDOWLESS FOR MAS GETS IMPROPER TIME OF DAY.
           NA03473      ACXE003 INT ECEC ERR: MESSAGE NOT UNDERSTOOD: #SETVALUE
           NA03564      MAS V2.2 TOOL REQUIRES 12 0 S FOR UNIVERSAL MAC ADDRESS
           NA03568      CONFIG TOOL 2.1, INTER EXEC ERROR MSG: NOT UNDERSTUD:# ASNUMBER
           NA03574      USER CANNOT SPECIFY PRIMARY IP ADDR ON INTERFACE
           NA03581      CONFIGURATOR ORDERS ISDN ADDRESSES NUMERICALLY
           NA03621      ERR MSG ACXE0003, INT EXEC ERROR, #GETOSPFDEFAULTCOSTFORINTFACE
           NA03622      X.25 STANDARDS MISSING FROM CFG TOOL PANEL
           NA03649      ACXE0003 INT. EXEC. ERROR: MESSAGE NOT UNDERSTOOD: #SPEC
           NA03650      ACXE0003 INT EXEC ERR: MESSAGE NOT UNDERSTOOD: #READSTREAM
           NA03668      SOME OF THE APPN CONFIGURATIONS ARE WIPPED OUT WHEN MIGRATE THE

NP00880   01/1998
           NA03288      CONFIGURATOR OPEN AND SAVE PERFORMANCE VERY SLOW
           NA03375      CONFIGURATOR CDB FILE GROWS TOO LARGE
           NA03429      CONFIG COMMAND LINE FACILITY STOPS UNTIL MOUSE IS MOVED

